Use All Attestation Subnets #5966
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nisdas
requested review from
rauljordan,
0xKiwi and
prestonvanloon
and removed request for
a team
rauljordan
approved these changes
May 23, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
Use all attestation subnets when broadcasting attestations.
What does this PR do? Why is it needed?
Instead of broadcasting attestations to a select few subnets, we instead
broadcast to all possible subnets so as to utilize all the nodes in the network.
Which issues(s) does this PR fix?
Part of #5935 and follows on from
ethereum/consensus-specs#1804 in the spec.
Other notes for review
N.A